Skip to content
This repository has been archived by the owner on Nov 1, 2023. It is now read-only.

Change How the agent detect it is running unmanaged #2521

Closed
Tracked by #2482
chkeita opened this issue Oct 17, 2022 · 0 comments · Fixed by #2649
Closed
Tracked by #2482

Change How the agent detect it is running unmanaged #2521

chkeita opened this issue Oct 17, 2022 · 0 comments · Fixed by #2649
Assignees
@chkeita

Comments

@chkeita
Copy link
Contributor

chkeita commented Oct 17, 2022 •
edited
Loading

The agent currently assumes that if it is running in a scaleset it is a managed node. We need to break that assumption and add a config to specify if the agent is running unmanaged or not.

AB#41825477
@chkeita chkeita mentioned this issue Oct 17, 2022
Closed
9 tasks
@ghost ghost added the Needs: triage label Oct 17, 2022
@chkeita chkeita self-assigned this Oct 17, 2022
This was referenced Nov 22, 2022
Merged
Merged
@ghost ghost locked as resolved and limited conversation to collaborators Dec 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@chkeita chkeita

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Making machine identity a parameter of the agent config chkeita/onefuzz
1 participant
@chkeita