SSWConsulting / SSWConsulting/SSW.Rewards.Mobile

✨ Create Tenant Parameter Files

Open
#1,502 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
37
Forks
11
PR merge metrics
No merged PRs in 30d

Description

Hi DevOps,

Pain

We need parameter files for each tenant environment to ensure deployments use the correct values and are repeatable.

Suggested Solution

Create parameter JSON files for each tenant and environment combination. Document the process for creating new tenant parameter files.

Implementation:

  • Create parameter files for SSW environments
  • Create TestCo dev parameters
  • Create template with documentation
Tasks
  • Create parameters/ssw-prod.json
  • Create parameters/ssw-staging.json
  • Create parameters/testco-dev.json
  • Create parameters/template.json with helpful comments
  • Document parameter file creation process
  • Validate parameter files against schema
  • Test deployments with each parameter file
  • Create parameter file naming convention guide
Acceptance Criteria
More Information

Files to Create:

  • NEW: infra/parameters/ssw-prod.json
  • NEW: infra/parameters/ssw-staging.json
  • NEW: infra/parameters/testco-dev.json
  • NEW: infra/parameters/template.json
  • NEW: Parameter files documentation

Dependencies: Previous PBI must be completed first

Epic: #1483

Thanks!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

First review the previous PBI and the parameter schema before creating infra/parameters/ssw-prod.json, infra/parameters/ssw-staging.json, infra/parameters/testco-dev.json, and infra/parameters/template.json. Document the naming and creation process, validate every file against the schema, and test deployments for each tenant environment; completion also requires the listed acceptance criteria.

Written by the indexing model from the issue text.

Assessment

Domain
devops, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.