You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Good idea, we can remove duplicated code and check on refactoring the file. Check for all the functions and might be make separate .sh for functions. Just my thought, need to investigate how much it would add value. Lets check on refactoring to make build script simple and understandable.
I think that BUILD_TAGS: secure should be enabled by default (and I will try to do it soon). But for ease of development, I plan to add a BUILD_TAGS:unsecure, but only as a tag for the build!
I think that BUILD_TAGS: secure should be enabled by default (and I will try to do it soon). But for ease of development, I plan to add a BUILD_TAGS:unsecure, but only as a tag for the build!
@tdrozdovsky Thank you for sharing your idea. I hope to set secure as a default.
In order to do so, it seems that the usability of Security Manager should be improved.
Let's talk about security components like Verifier and Authenticator by opening a new issue.
How about refactoring
build.sh
file a little bit shorter?PKG_LIST
and use a relative path to run test scenarios.BUILD_TAGS
such assecure
,mnedc
.The text was updated successfully, but these errors were encountered: