You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per the Tailscale docs it looks like tags have to be defined in an ACL before they're applied to devices. Looks like either defining the bastion tag is missing from the instructions/code or Tailscale used to create this tag by default on the back end and no longer does.
The text was updated successfully, but these errors were encountered:
Grant the ability to advertise the routes as you noted above. Just for clarity, the routes you listed above above are "the CIDR blocks of any VPCs you want on your VPN, which must not collide", correct?
Also, I do not see a way to define the ACL programmatically: While there is a tailscale.Acl resource, I don't see any obvious way to work with the existing ACL they provide for you. Can you confirm this matches your understanding and that the user will need to manually edit these?
When creating a new AWS bastion host, the userdata script will fail because of the
--advertise-tags
param:Relevant line: https://github.com/jaxxstorm/pulumi-tailscale-bastion/blob/main/provider/pkg/provider/aws/userdata.tmpl#L21
Per the Tailscale docs it looks like tags have to be defined in an ACL before they're applied to devices. Looks like either defining the
bastion
tag is missing from the instructions/code or Tailscale used to create this tag by default on the back end and no longer does.The text was updated successfully, but these errors were encountered: