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

Merge proxy-processor branch #626

Open
Haishi2016 opened this issue Jan 30, 2025 · 1 comment
Open

Merge proxy-processor branch #626

Haishi2016 opened this issue Jan 30, 2025 · 1 comment

Comments

@Haishi2016
Copy link
Contributor

We need to work on merging the proxy-processor branch, unless this is overriden by the new remote agent work.
An associated issue is that when a stage is activated we are not including stage spec in the activation. In current implementation the process does another query back to the API to retrieve latest stage spec. We should probably change it so that the stage activation data is self-contained and no additional lookup is necessary.

@msftcoderdjw
Copy link
Contributor

@Haishi2016 please rebase proxy-processor branch at first to unblock customer at first. We also have another task to support campaign on new remote agent.

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

2 participants