David JENNI

since GH import-solution action is a thin wrapper (and you already reproed that pac CLI stand alone succeeds): still unclear if this a action/CLI bug or if this is more...

@gabrielesilvagni sorry for the delay in reply :-( investigating on our side; since you have not attached any error spew, I assume in your case, the action succeeded without showing...

the create-environment actions simply hands the list of templates through to the EnvManagement API. If this reproes, we would need a more detailed log for us to have our partner...

thanks, we'll take this into consideration as a, for now, lower prio improvement. The team is still working on getting more actions online.

@korytiak that by itself won't help in all situation, e.g. when using appID/ClientSecret authN, the OAuth access token expires after 60 min and the current MSAL ConfidentialClientAppBuilder doesn't offer to...

@nkirstein the underlying reason for the authN error is that for appID/clientSecret, the MSAL library offers no way to refresh the OAuth access token (i.e. no refresh token). And our...

in recent releases of both pac CLI and the pp-actions tasks, we've added a more robust renewal for MSAL confidential apps by holding on to the client secret for the...

>I think in this particular case we should include the new work as the feature isn't terribly useful without being able to pass the role name. I was originally thinking/suggesting...

while our mutual teams work on our roadmap, I'm converting this issue to a discussion.

@orangetoken we're taking this under consideration, and if approved, we'll apply the same logic to `pac org list` while the code change in pac CLI is trivial in itself, the...