poetry add git+ssh://git@github.com/org/private-repo.git
Based on https://github.com/python-poetry/poetry/issues/835#issuecomment-600773746
poetry add git+ssh://git@github.com/org/private-repo.git
Based on https://github.com/python-poetry/poetry/issues/835#issuecomment-600773746
DRY is one of key principles in software development.
I was happy to see OpenAPI schema can be extended if needed and wanted to benefit from it
"jira_cloud_input": {"type": "object","properties": {"api_token": {"type": "string"},"name": {"type": "string"},"from": {"type": "string"},"interval": {"type": "string"},"index": {"type": "string"}},"xml": {"name": "jira_cloud_input","attribute": false,"wrapped": false}},"jira_cloud_input_disabled": {"allOf": [{"$ref": "#/components/schemas/jira_cloud_input"},{"type": "object","properties": {"disabled": {"type": "string","enum": ["0","1"]}}}]}
This looks nice in Swagger Editor
Relevant endpoint definitions also look as expected:What is generated from "standard" schema definition looks fine
Unfortunately, where the extension was used lacks of method parameters
As a consequence, I need to break DRY rule just to have reliable client code generated.
PS: I do use swagger-codegen-cli-v3 docker image in fact to generate the client code
I was working on AWS lab with ASA recently.
There is fantastic step-by-step instruction. When going through it, pay attention there is sub-instruction you should implement first.
Anyway, once I was to finish the ASA instruction, there was no connection from the internet to ASA management. I had "jump host" as a "side effect" of the sub-instruction, so I was able to connect via private IP address.
Issue was in route table - lack of entry for internet gateway. See this troubleshooting instruction for a reference.
I was installing Sysmon For Linux with use of the project instructions.
Once sysmon is installed, it requires to accept EULA and start with some configuration - see relevant paragraph in the project documentation.
Let me describe general rules before going into details:
Let me start from distributions where the instructions were sufficient:
sudo dnf search wgetsudo dnf install -y wget
sudo zypper install -y libicusudo rpm --import https://packages.microsoft.com/keys/microsoft.ascwget -q https://packages.microsoft.com/config/sles/15/prod.reposudo mv prod.repo /etc/zypp/repos.d/microsoft-prod.reposudo chown root:root /etc/zypp/repos.d/microsoft-prod.reposudo zypper install -y sysmonforlinux
Let's come to cases where the instruction failed:
sudo apt-get install sysmonforlinux
ends with error
Unable to locate package sysmonforlinux
If package for Ubuntu 21.04 is used all seems to work fine - sysmon was started and all of 8 Event IDs are returned. Content also looks fine at first glance, but I'm not sure about details.
[root@ip-172-31-10-70 fedora]# sysmon -accepteula -i /tmp/all_rules_included.xmlSysmon v1.0.2 - Monitors system eventsSysinternals - www.sysinternals.comBy Mark Russinovich, Thomas Garnier and Kevin SheldrakeCopyright (C) 2014-2021 Microsoft CorporationUsing libxml2. libxml2 is Copyright (C) 1998-2012 Daniel Veillard. All Rights Reserved.Loading configuration file with schema version 4.60Sysmon schema version: 4.81Configuration file validated.Job for sysmon.service failed because the control process exited with error code.See "systemctl status sysmon.service" and "journalctl -xeu sysmon.service" for details.[root@ip-172-31-10-70 fedora]# systemctl status sysmon.service× sysmon.service - Sysmon event loggerLoaded: loaded (/etc/systemd/system/sysmon.service; enabled; vendor preset: disabled)Active: failed (Result: exit-code) since Fri 2022-09-09 10:36:37 UTC; 5s agoProcess: 15510 ExecStart=/opt/sysmon/sysmon -i /opt/sysmon/config.xml -service (code=exited, status=13)CPU: 5.781sSep 09 10:36:37 ip-172-31-10-70.us-west-1.compute.internal sysmon[15557]: /opt/sysinternalsEBPF/sysinternalsEBPF_offsets.confSep 09 10:36:37 ip-172-31-10-70.us-west-1.compute.internal sysmon[15510]: Telemetry failed to start: Configuration could not be loadedSep 09 10:36:37 ip-172-31-10-70.us-west-1.compute.internal systemd[1]: sysmon.service: Control process exited, code=exited, status=13/n/aSep 09 10:36:37 ip-172-31-10-70.us-west-1.compute.internal sysmon[15557]: <Event><System><Provider Name="Linux-Sysmon" Guid="{ff032593-a8d3-4f13-b0d6-01fc615a0f97}"/><EventID>4</EventID><Version>3</Version><Level>4</Level><Task>4</Task><Opcode>0</Opco>Sep 09 10:36:37 ip-172-31-10-70.us-west-1.compute.internal sysmon[15557]: Stopping....Sep 09 10:36:37 ip-172-31-10-70.us-west-1.compute.internal sysmon[15557]: Total events: 0, bad events: 0, ratio = -nanSep 09 10:36:37 ip-172-31-10-70.us-west-1.compute.internal sysmon[15557]: Lost events: 0, in 0 notificationsSep 09 10:36:37 ip-172-31-10-70.us-west-1.compute.internal systemd[1]: sysmon.service: Failed with result 'exit-code'.Sep 09 10:36:37 ip-172-31-10-70.us-west-1.compute.internal systemd[1]: Failed to start Sysmon event logger.Sep 09 10:36:37 ip-172-31-10-70.us-west-1.compute.internal systemd[1]: sysmon.service: Consumed 5.781s CPU time.
The error suggests issue with the package, so no solution was tried.
fatal: [X.XXX.XX.XXX]: FAILED! => {"changed": true, "cmd": "sudo apt-get updatesudo apt-get install apt-transport-httpssudo apt-get updatesudo apt-get install sysmonforlinux", "delta": "0:00:03.241709", "end": "2022-09-06 10:24:14.629355", "msg": "non-zero return code", "rc": 100, "start": "2022-09-06 10:24:11.387646", "stderr": "W: GPG error: https://packages.microsoft.com/debian/10/prod buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EB3E94ADBE1229CFE: The repository 'https://packages.microsoft.com/debian/10/prod buster InRelease' is not signed.W: GPG error: https://packages.microsoft.com/debian/10/prod buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EB3E94ADBE1229CFE: The repository 'https://packages.microsoft.com/debian/10/prod buster InRelease' is not signed.E: Unable to locate package sysmonforlinux", "stderr_lines": ["W: GPG error: https://packages.microsoft.com/debian/10/prod buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EB3E94ADBE1229CF", "E: The repository 'https://packages.microsoft.com/debian/10/prod buster InRelease' is not signed.", "W: GPG error: https://packages.microsoft.com/debian/10/prod buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EB3E94ADBE1229CF", "E: The repository 'https://packages.microsoft.com/debian/10/prod buster InRelease' is not signed.", "E: Unable to locate package sysmonforlinux"], "stdout": "Hit:1 http://security.debian.org/debian-security buster/updates InReleaseHit:2 http://cdn-aws.deb.debian.org/debian buster InReleaseHit:3 http://cdn-aws.deb.debian.org/debian buster-updates InReleaseGet:4 https://packages.microsoft.com/debian/10/prod buster InRelease [29.8 kB]Err:4 https://packages.microsoft.com/debian/10/prod buster InReleaseThe following signatures couldn't be verified because the public key is not available: NO_PUBKEY EB3E94ADBE1229CFHit:5 http://cdn-aws.deb.debian.org/debian buster-backports InReleaseReading package lists...Reading package lists...Building dependency tree...Reading state information...apt-transport-https is already the newest version (1.8.2.3).0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.Hit:1 http://security.debian.org/debian-security buster/updates InReleaseHit:2 http://cdn-aws.deb.debian.org/debian buster InReleaseHit:3 http://cdn-aws.deb.debian.org/debian buster-updates InReleaseHit:4 http://cdn-aws.deb.debian.org/debian buster-backports InReleaseGet:5 https://packages.microsoft.com/debian/10/prod buster InRelease [29.8 kB]Err:5 https://packages.microsoft.com/debian/10/prod buster InReleaseThe following signatures couldn't be verified because the public key is not available: NO_PUBKEY EB3E94ADBE1229CFReading package lists...Reading package lists...Building dependency tree...Reading state information...", "stdout_lines": ["Hit:1 http://security.debian.org/debian-security buster/updates InRelease", "Hit:2 http://cdn-aws.deb.debian.org/debian buster InRelease", "Hit:3 http://cdn-aws.deb.debian.org/debian buster-updates InRelease", "Get:4 https://packages.microsoft.com/debian/10/prod buster InRelease [29.8 kB]", "Err:4 https://packages.microsoft.com/debian/10/prod buster InRelease", " The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EB3E94ADBE1229CF", "Hit:5 http://cdn-aws.deb.debian.org/debian buster-backports InRelease", "Reading package lists...", "Reading package lists...", "Building dependency tree...", "Reading state information...", "apt-transport-https is already the newest version (1.8.2.3).", "0 upgraded, 0 newly installed, 0 to remove and 5 not upgraded.", "Hit:1 http://security.debian.org/debian-security buster/updates InRelease", "Hit:2 http://cdn-aws.deb.debian.org/debian buster InRelease", "Hit:3 http://cdn-aws.deb.debian.org/debian buster-updates InRelease", "Hit:4 http://cdn-aws.deb.debian.org/debian buster-backports InRelease", "Get:5 https://packages.microsoft.com/debian/10/prod buster InRelease [29.8 kB]", "Err:5 https://packages.microsoft.com/debian/10/prod buster InRelease", " The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EB3E94ADBE1229CF", "Reading package lists...", "Reading package lists...", "Building dependency tree...", "Reading state information..."]}
There were two solutions applied, but none resolved the issue
sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com EB3E94ADBE1229CF
sudo apt update
curl https://packages.microsoft.com/keys/microsoft.asc | sudo apt-key add -