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

The external link does not show up in the txt report #559

Open
zhukovgreen opened this issue Aug 10, 2020 · 1 comment
Open

The external link does not show up in the txt report #559

zhukovgreen opened this issue Aug 10, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@zhukovgreen
Copy link
Contributor

zhukovgreen commented Aug 10, 2020

The external link does not show up in the txt report. @shaded-enmity, @pirat89, is that expected?

Risk Factor: high (inhibitor)
Title: Local repository identified
Summary: Local repository found (baseurl starts with file:///). Currently leapp is not supporting this option.
Remediation: [hint] By using Apache HTTP Server you can expose your local repository via http. See the linked article for details. 
----------------------------------------

Originally posted by @bocekm in #531

The fix should be easy:
https://github.com/oamg/leapp/blob/af8730d5076659bcdc4ab0c2b09b6b408e95dcd3/leapp/utils/report.py#L91

@zhukovgreen zhukovgreen added the enhancement New feature or request label Aug 10, 2020
@zhukovgreen zhukovgreen changed the title The external link does not show up in the txt report. @shaded-enmity, @pirat89, is that expected? The external link does not show up in the txt report Aug 10, 2020
MichalHe pushed a commit to MichalHe/leapp-repository that referenced this issue Jun 21, 2022
Currently, when tested actor runs and tries to access workflow
config, it fails with WorkflowConfigNotAvailable. Apart from
feeding the actor a mock config model, we need to also make
it aware it should us the config.
@pirat89 pirat89 pinned this issue Mar 7, 2023
@pirat89
Copy link
Member

pirat89 commented Mar 7, 2023

most likely, this is going to be improved for the next release (@oamg/developers ); pinned issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants