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

Change await log type to cloud-ready-check lib #1855

Merged
merged 1 commit into from Jan 6, 2022

Conversation

lblackstone
Copy link
Member

Proposed changes

The cloud-ready-check library includes an identical
logging.Message type definition, so remove the type
from the provider and update all references to use the
external type instead.

Related issues (optional)

@github-actions
Copy link

github-actions bot commented Jan 5, 2022

Does the PR have any schema changes?

Looking good! No breaking changes found.
No new resources/functions.

2 similar comments
@github-actions
Copy link

github-actions bot commented Jan 5, 2022

Does the PR have any schema changes?

Looking good! No breaking changes found.
No new resources/functions.

@github-actions
Copy link

github-actions bot commented Jan 5, 2022

Does the PR have any schema changes?

Looking good! No breaking changes found.
No new resources/functions.

The cloud-ready-check library includes an identical
logging.Message type definition, so remove the type
from the provider and update all references to use the
external type instead.
@lblackstone lblackstone force-pushed the lblackstone/external-logger-defs branch from 95c9674 to 4166b9f Compare January 5, 2022 22:58
@github-actions
Copy link

github-actions bot commented Jan 5, 2022

Does the PR have any schema changes?

Looking good! No breaking changes found.
No new resources/functions.

@@ -1,4 +1,4 @@
// Copyright 2016-2019, Pulumi Corporation.
// Copyright 2016-2022, Pulumi Corporation.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this file be in cloud-ready-checks instead?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this logic is more specific to provider logging, so I decided to leave it here. The await library returns the messages and it's up to the client how to handle them.

@@ -1,4 +1,4 @@
// Copyright 2016-2019, Pulumi Corporation.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here

@@ -1,4 +1,4 @@
// Copyright 2016-2019, Pulumi Corporation.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here.

@lblackstone lblackstone merged commit 6be4f44 into master Jan 6, 2022
@pulumi-bot pulumi-bot deleted the lblackstone/external-logger-defs branch January 6, 2022 01:06
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

Successfully merging this pull request may close these issues.

None yet

2 participants