Allow to specify package version
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- devops, operating-systems
Research direction
Start by locating where the extension defines and invokes the shown zypper update and security-patch commands. Trace how package selections are supplied, then define how a customer-provided version reaches the command and verify that the resulting installation pins the requested version.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
My customers are not able to specify a version. This is problematic as they roll patches out to lower environments first, and sometimes (often times) by the time they get to prod, the version pushed by this agent will be different than what was tested in lower environments.
Describe the solution you'd like
Allow the customer to specify an image version. In zypper, you can do:
zypper install <package_name>=
But the extension doesn't expose the version:
# Install update
self.single_package_upgrade_cmd = 'sudo zypper --non-interactive update '
self.zypper_install_security_patches = 'sudo zypper --non-interactive patch --category security'
Describe alternatives you've considered
The customer is working to accelerate their patching cycle, but no workaround exists with the extension itself that I am aware of.
- Dominant language
- Python
- Stars
- 12
- Forks
- 20
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/LinuxPatchExtension
-
Difficulty 2/5 Half a day Newbie friendliness 68/100
Azure/LinuxPatchExtension#350 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Azure/LinuxPatchExtension#381 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Azure/LinuxPatchExtension#369 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
Azure/LinuxPatchExtension#339 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Azure/LinuxPatchExtension#337 · 1 comment ·
All issues in Azure/LinuxPatchExtension
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
learningequality/ricecooker#747 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
BSData/horus-heresy-3rd-edition#3171 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
run-llama/llama_index#23199 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
KhronosGroup/glTF-Blender-IO#2769 ·