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

Azure builder usage without client_id and client_secret #180

Open
Arlington1985 opened this issue Aug 4, 2020 · 0 comments
Open

Azure builder usage without client_id and client_secret #180

Arlington1985 opened this issue Aug 4, 2020 · 0 comments

Comments

@Arlington1985
Copy link

packerlicious version

1.5.0

Expected behavior

Possibility using only with Subscription_id

https://www.packer.io/docs/builders/azure

If your organization allows it, you can use a command line interactive login method based on oAuth 'device code flow'. Packer will select this method when you only specify a subscription_id in your builder configuration. When you run Packer, it will ask you to visit a web site and input a code. This web site will then authenticate you, satisfying any two-factor authentication policies that your organization might have. The tokens are cached under the .azure/packer directory in your home directory and will be reused if they are still valid on subsequent runs.

Actual behavior

    raise ValueError(msg)
ValueError: Resource client_id required in type azure-arm

Steps to reproduce

Use Azure builder without setting client_id

template.add_builder(
    builder.Azure(
            tenant_id="xxx-xxx-xxx-xxx-xxxxx",
            subscription_id=Ref('subscription_id'),
            managed_image_resource_group_name = Ref('resource_name'),
        )
)
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

No branches or pull requests

1 participant