Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ Refactor ] Consider aligning TOWER_AWS_* keys to AWS equivalents #111

Open
2 of 3 tasks
gwright99 opened this issue Jul 5, 2024 · 0 comments
Open
2 of 3 tasks
Assignees

Comments

@gwright99
Copy link
Collaborator

gwright99 commented Jul 5, 2024

The ssm_sensitive_values_seqerakit.json contains 3 AWS entries (representing the 3 available fields for an AWS-type credential).

While pursuing an unassisted implementation, a recent custom found the key names unclear and requested clarificiation. We should consider renaming these two keys to align with the standard AWS names:

  • AWS_ACCESS_KEY_ID
  • AWS_SECRET_ACCESS_KEY

TO DO

  • Determine if this change affects any logic elsewhere in the tool.
  • Determine if making this change to an existing implementation breaks anything (unlikely but best to confirm).
  • Align (if necessary) Ansible values, primarily in 06_run_seqerakit.yml.tpl
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants