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

Tailnet policy file keys not preserving case when generated using an Acl resource #115

Open
johanblomgren opened this issue Apr 12, 2023 · 1 comment
Labels
kind/bug Some behavior is incorrect or out of spec

Comments

@johanblomgren
Copy link

What happened?

When managing a Tailscale policy file using a Pulumi Tailscale Acl resource, keys submitted as part of the Acl resource configuration gets transformed to lower case. For example:

const policy = new tailscale.Acl("policy", {acl: JSON.stringify({
    autoApprovers: {},
})});

The preview will indeed preserve case:

... \\\"autoApprovers\\\":{} ...

However, inspecting the generated policy file in the Tailscale UI will show autoapprovers: {}.

Expected Behavior

Case should be preserved when generating and updating the Tailscale policy file.

Steps to reproduce

Create any Acl resource containing a "camelCase" formatted key such as autoApprovers.

const policy = new tailscale.Acl("policy", {acl: JSON.stringify({
    autoApprovers: {},
})});

Review generated policy file using the Tailscale UI and check case for that key.

Output of pulumi about

CLI
Version 3.62.0
Go Version go1.20.2
Go Compiler gc

Host
OS darwin
Version 13.0.1
Arch arm64

Backend
Name pulumi.com

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@johanblomgren johanblomgren added kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team labels Apr 12, 2023
@jazzyfresh jazzyfresh removed the needs-triage Needs attention from the triage team label Apr 14, 2023
@jazzyfresh
Copy link

Thank you for reporting this! This has been added to our project board

@mikhailshilkov mikhailshilkov added kind/bug Some behavior is incorrect or out of spec and removed kind/bug Some behavior is incorrect or out of spec labels Jun 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec
Projects
None yet
Development

No branches or pull requests

3 participants