Adam Grare
Adam Grare
Currently we have a separate `provider_worker` script which is able to start non-rails workers by passing options and secrets to stdin then exec'ing the worker. Having this as a standalone...
When plugins run tests on a release branch the Gemfile.lock.release was copied to Gemfile.lock but since the plugin spec doesn't match (GIT vs PATH) the Gemfile.lock was invalidated and rebuilt...
This is an ongoing list of items which need to be extracted out of core repos (manageiq, manageiq-api, manageiq-ui) and into plugins. A continuation of https://github.com/ManageIQ/manageiq/issues/14840 ## Specs - [...
The `#find` method introduces a dependency ordering issue during full refresh and a potential missing data issue during targeted refresh and should be replaced by `#lazy_find` wherever possible. This method...
If a worker crashes early in startup it leaves a worker record in `:status => "creating"`. This record is never cleaned up but counts as "starting" so new workers are...
It is possible for the workers and the miq_worker rows to get out of sync https://github.com/ManageIQ/manageiq/issues/22644
Required for: * https://github.com/ManageIQ/manageiq-providers-workflows/pull/57 TODO: - [x] `ManageIQ::Providers::EmbeddedAutomationManager::ConfigurationScriptSource` won't create without a git_repository
### Discussed in https://github.com/orgs/ManageIQ/discussions/22877 Originally posted by **bfilion87** February 5, 2024 Hello, I am trying to update a service template item that we use as part of a service catalog...
We don't want to allow the creation of non-leaf providers in production/development but for specs this requirement pushes us to having specific provider plugins be the prototypical providers for these...
Everytime I read this method my head hurts, time to fix it