Skip to content

Task install_managed security_type not being respected with 04t ID #3902

@jimmythorne10

Description

@jimmythorne10

Describe the bug

When I use teh "install_managed" task to install a managed package with the --version '04t...' parameter and the --security_type NONE parameter, I end up getting the packaged installed for all users instead of admins only. If I, instead, use the version number (1.11.2), it works fine unless there are multiple managed packages with the same namespace (extensions).

Image

Reproduction steps

  1. Run command with above constraints with a version that introduces a new tab
  2. Login to Org.
  3. Open non-admin profile
  4. Tab is available for the profile in Object Settings

Your CumulusCI and Python versions

CumulusCI version: 4.3.0 (C:\users\jimmy thorne.local\bin\cci)
Python version: 3.12.1 (C:\Users\Jimmy Thorne\AppData\Local\pipx\pipx\venvs\cumulusci\Scripts\python.exe)

Operating System

Windows 10 Pro

Windows environment

Bash on Windows

CumulusCI installation method

pipx

Error Gist

No response

Additional information

I've tested this on 1GP and 2GP packaging with the same results. Ideally, I'd love to be able to use the 04t identifier instead of the version number due to the error in the screenshot above.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions