bcgov / bcgov/cloud-pathfinder
[BUG]: Current sample containers app policies are unable to deploy the app
- Dominant language
- Jinja
- Stars
- 2
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the Issue**
As QA/user advocate I want the sample containers app can be used, as it is, with minimum changes, but the end users.
The sample containers app now uses OIDC protocols to authenticate in front of AWS. OIDC requires the user to create roles that will be used at deployment time. These roles have policies attached to it. Currently the sample containers app repo contains policy templates to use. The user is required to change several elements like the account number and licence plate.
The sample containers app uses two environments: **_dev_** and _**tools**_. Each of them requires a AWS role and each tole has policies attached to it.
Unfortunately, as the policies are currently crafted, the ones associated to the _Tools_ environment are unable to deploy the app. To be more precise, the **_docker_push_** job of the **_push_** GitHub action fails (this job uses the _tools_ environment (Note: the current policies for the _dev_ environment work, and also the policies for the _tools_ for the **_Deploy Tools_** GitHub action)
**Additional Context**
The policy files are the following
For dev environment
- App_Deployment_IAM_Policy_Part1.json
- App_Deployment_IAM_Policy_Part2.json
For Tools environment
- Registry_Deployment_IAM_Policy_for_Containers_App_Part1.json
- Registry_Deployment_IAM_Policy_for_Containers_App_Part2.json
**Acceptance Criteria**
- Refactor policies for sample containers app so app can be deployed
- This set of policies should be have the minimum necessary permissions
- Upload the new policies to the startup-sample-project-aws-containers repo
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.