Remove the need for AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY to be set with Digital Ocean deployment

[costrouc]

Closes #1343

Changes introduced in this PR:

AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY will be automatically set based on SPACES_ACCESS_KEY_ID and SPACES_SECRET_ACCESS_KEY.

Types of changes

What types of changes does your PR introduce?

Put an x in the boxes that apply

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds a feature)
• Breaking change (fix or feature that would cause existing features to not work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build related changes
• Other (please describe):

Testing

Requires testing

• Yes
• No

Further comments (optional)

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered and more.

[costrouc]

@viniciusdc this will allow you to remove the need for setting those environment variables for the Digital Ocean deploymet.

[viniciusdc]

LGTM, thanks for updating this @costrouc

[viniciusdc]

@costrouc may I ask if you can do a DO render over this branch to validate if everything works? -- as the CI envs here possess all the necessary keys already, we might be unable to identify some exceptions

[viniciusdc]

I will be testing this on DO, today

[viniciusdc]

Tested with remote DO deployment and no AWS credentials, all working !!!

[viniciusdc]

HI @costrouc sorry for the messy revert there, It seems that the destroy command failed with missing environments -- I tried adding a quick workaround, but the error persisted so I reverted the PR.

[viniciusdc]

to fix the destroy part we just need to add the new terraform state context manager in gather_stage_outputs and destroy_stages of destroy.py