-
Notifications
You must be signed in to change notification settings - Fork 0
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
S175 initial version #1
base: main
Are you sure you want to change the base?
Conversation
Co-authored-by: aperez-worklytics <[email protected]>
- Add extra settings (bulk and github) - Make script filename variable (multiple connections to the same source) - Delete `kind` setting (AWS context given)
- Missing tenant API host - Define extra settings
Optional attributes (`module_variable_optional_attrs`) was an experimental feature in 1.1.x - 1.2.x versions, and our official Psoxy docs explicitly states that Terraform 1.3.x is a requirement
@jlorper this is ready; fully tested (see https://github.com/Worklytics/evalengin/pull/6934) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't get how the connectors are filled in, if it is manual (which appears to be) is a waste of time for the customer. We should reuse the proxy output.
runs-on: ubuntu-latest | ||
strategy: | ||
matrix: | ||
terraform_version: [ '~1.5.0', '~1.6.0', '~1.7.0', 'latest'] # in theory, we go down to 1.3, but I think that's overkill for lint |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
starting rc-0.5 this is >= 1.6
https://github.com/Worklytics/psoxy/blob/rc-v0.5.0/.github/workflows/ci-terraform-modules.yaml
So adapt everywhere please
should be to create the actual connection in the [Data Sources] section of the Worklytics Web App. These submodules | ||
provide a way to automate this process. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should be to create the actual connection in the [Data Sources] section of the Worklytics Web App. These submodules | |
provide a way to automate this process. | |
should be to create the actual connection in the [Data Sources] section of the Worklytics Web App, either manually following the instructions in the TO-DO files, or automatically with a script that is produced by these sub-modules. |
not totally sold on this... what do you think?
See task for details (comments on modules structure): Tenant API: Terraform AWS modules.