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

aws_appstream_stack error #25390

Open
PatriQ1414 opened this issue Jun 16, 2022 · 2 comments
Open

aws_appstream_stack error #25390

PatriQ1414 opened this issue Jun 16, 2022 · 2 comments
Labels
bug Addresses a defect in current functionality. service/appstream Issues and PRs that pertain to the appstream service. stale Old or inactive issues managed by automation, if no further action taken these will get closed. waiting-response Maintainers are waiting on response from community or contributor.

Comments

@PatriQ1414
Copy link

PatriQ1414 commented Jun 16, 2022

After successfully deploying appstream, I get the following error whenever I run a terraform apply

│ Error: Provider produced inconsistent final plan

│ When expanding the plan for aws_appstream_stack.appstream to include new values learned so far during apply, provider "registry.terraform.io/hashicorp/aws" produced an invalid new value for .user_settings: actual set element
│ cty.ObjectVal(map[string]cty.Value{"action":cty.StringVal("CLIPBOARD_COPY_FROM_LOCAL_DEVICE"), "permission":cty.StringVal("ENABLED")}) does not correlate with any element in plan.

│ This is a bug in the provider, which should be reported in the provider's own issue tracker.


│ Error: Provider produced inconsistent final plan

│ When expanding the plan for aws_appstream_stack.appstream to include new values learned so far during apply, provider "registry.terraform.io/hashicorp/aws" produced an invalid new value for .user_settings: actual set element
│ cty.ObjectVal(map[string]cty.Value{"action":cty.StringVal("DOMAIN_PASSWORD_SIGNIN"), "permission":cty.StringVal("ENABLED")}) does not correlate with any element in plan.

│ This is a bug in the provider, which should be reported in the provider's own issue tracker.


│ Error: Provider produced inconsistent final plan

│ When expanding the plan for aws_appstream_stack.appstream to include new values learned so far during apply, provider "registry.terraform.io/hashicorp/aws" produced an invalid new value for .user_settings: actual set element
│ cty.ObjectVal(map[string]cty.Value{"action":cty.StringVal("DOMAIN_SMART_CARD_SIGNIN"), "permission":cty.StringVal("DISABLED")}) does not correlate with any element in plan.

│ This is a bug in the provider, which should be reported in the provider's own issue tracker.


│ Error: Provider produced inconsistent final plan

│ When expanding the plan for aws_appstream_stack.appstream to include new values learned so far during apply, provider "registry.terraform.io/hashicorp/aws" produced an invalid new value for .user_settings: block set length changed from 4 to 7.

│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

appstream error

@github-actions github-actions bot added needs-triage Waiting for first response or review from a maintainer. bug Addresses a defect in current functionality. labels Jun 16, 2022
@justinretzolk
Copy link
Member

Hey @PatriQ1414 👋 Thank you for taking the time to raise this! So that we have all of the necessary information in order to look into this, can you update the issue description to include all of the information requested in the bug report template?

@justinretzolk justinretzolk added waiting-response Maintainers are waiting on response from community or contributor. service/appstream Issues and PRs that pertain to the appstream service. and removed needs-triage Waiting for first response or review from a maintainer. labels Jun 16, 2022
Copy link

github-actions bot commented Jun 5, 2024

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

@github-actions github-actions bot added the stale Old or inactive issues managed by automation, if no further action taken these will get closed. label Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Addresses a defect in current functionality. service/appstream Issues and PRs that pertain to the appstream service. stale Old or inactive issues managed by automation, if no further action taken these will get closed. waiting-response Maintainers are waiting on response from community or contributor.
Projects
None yet
Development

No branches or pull requests

2 participants