[Cloud Security] Create Serverless QA Environment #1982
Conversation
📊 Allure Report - 💚 No failures were reported.
|
|
@Omolola-Akinleye, The last workflow's successful run didn't involve destroying the environment. Can you please ensure that the destruction process is also functioning correctly? |
@gurevichdmitry I created another workflow and also deleted the workflow. |
| @@ -17,6 +17,8 @@ AWS_REGION="eu-west-1" # Add your desired default AWS region here | |||
| DELETED_ENVS=() | |||
| FAILED_ENVS=() | |||
|
|
|||
| : "${TF_VAR_qa_ec_api_key:?Please set TF_VAR_qa_ec_api_key with an Elastic QA Cloud API Key}" | |||
There was a problem hiding this comment.
@Omolola-Akinleye I'm unsure if this is the appropriate location to request the TF_VAR_qa_ec_api_key. Since I intend to delete a production environment, the TF_VAR_qa_ec_api_key isn't necessary. If I define it here, both keys would be required.
There was a problem hiding this comment.
@Omolola-Akinleye I've updated the branch and it appears that the CI is failing due to linting issues. Could you please fix them?
Summary of your changes
This PR creates a Serverless QA Environment. In this PR we updated
Mask Sensitive Datato update theTF_VAR_ec_api_keywith the secrets QA API KEY wheninput.ec-urlishttps://console.qa.cld.elstc.co.Also, we added options
Screenshot/Data
Related Issues
elastic/kibana#176748