-
Notifications
You must be signed in to change notification settings - Fork 35
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
Migrate the Datadog::IAM::User resource to the python 3.7 runtime #91
Conversation
@@ -0,0 +1 @@ | |||
__version__ = "2.0.0" |
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.
maybe 1.2.0 instead ? No need for major since it should be transparent to the user right ?
__version__ = "2.0.0" | |
__version__ = "1.2.0" |
last released version was 1.1.0 https://github.com/DataDog/datadog-cloudformation-resources/releases/tag/datadog-iam-user-1.1.0
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.
Yeah, since there are no changes to the schema, I think we can do a minor. Though for now I'll just bump this to dev anyway and we can bump to the proper version at release time.
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.
__version__ = "2.0.0" | |
__version__ = "1.2.0.dev" |
model.DatadogCredentials.ApiKey, | ||
model.DatadogCredentials.ApplicationKey, | ||
model.DatadogCredentials.ApiURL or "https://api.datadoghq.com", | ||
TYPE_NAME, |
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.
My mistake, let's not use TYPE_NAME
directly here, and instead create a new constant with value iam-user
to keep the same value as the java version
Line 25 in 06c00b8
return ApiClients.V1Client(apiKey, appKey, apiURL, "iam-user", version); |
I went with TELEMETRY_TYPE_NAME
resourceModel=model, | ||
) | ||
|
||
LOG.info("Starting the User Resource Create Handler") |
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.
nit: let's use the TYPE_NAME here
LOG.info("Starting the User Resource Create Handler") | |
LOG.info("Starting %s Create Handler", TYPE_NAME) |
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 went with f strings :)
@@ -0,0 +1,3 @@ | |||
cloudformation-cli-python-lib==2.1.2 | |||
git+https://github.com/datadog/datadog-api-client-python.git@750a42c58c6246d4a0a14920c438c8986a41a7bd |
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.
can be removed as it is a dep of common
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'm going to revisit this requirements entirely once we tag a first version of the common. I'll fix both this and the monitor resource deps in a followup PR once we do that.
Co-authored-by: Hippolyte HENRY <zippolyte@users.noreply.github.com>
Co-authored-by: Hippolyte HENRY <zippolyte@users.noreply.github.com>
What does this PR do?
This PR migrates the Datadog::IAM::User resource to the python 3.7 runtime. I tested this using the approach being documented here - https://github.com/DataDog/datadog-cloudformation-resources/pull/90/files
Since there are no JSON schema changes, this should be a mostly transparent migration for users of the resource