Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / Azure/azure-functions-powershell-library issues and pull requests
#54 - Add public pipeline
Pull Request -
State: closed - Opened by andystaples 5 months ago
#53 - Add 1ES Official ADO pipeline
Pull Request -
State: closed - Opened by andystaples 5 months ago
#52 - Add Code Mirror pipeline yaml
Pull Request -
State: closed - Opened by andystaples 5 months ago
#51 - Added CodeQL file for Onboarding
Pull Request -
State: open - Opened by aditya921 5 months ago
#50 - Remove AzureWebJobsStorage from local.settings.json
Pull Request -
State: closed - Opened by Francisco-Gamino 5 months ago
#49 - Hard crash with `func start` using .NET 8 preview 5
Issue -
State: open - Opened by paulyuk over 1 year ago
#48 - Enable .NET 8 Preview 5 with PowerShell module
Issue -
State: open - Opened by paulyuk over 1 year ago
- 1 comment
#47 - Add releases for this repo
Issue -
State: open - Opened by paulyuk over 1 year ago
#46 - PowerShell gallery for AzureFunctions.PowerShell.SDK needs Project Site link
Issue -
State: open - Opened by paulyuk over 1 year ago
#44 - [bug bash] Update parsing error formatting to include single quotes for the function name and attribute that is incorrect
Issue -
State: open - Opened by Francisco-Gamino over 1 year ago
#43 - When parsing a PowerShell function, we need a way to specify a session context with modules which are only available to the function app
Issue -
State: open - Opened by Francisco-Gamino over 1 year ago
#42 - Update module PowerShell 7.2 SDK to 7.2.9
Issue -
State: open - Opened by Francisco-Gamino almost 2 years ago
#41 - Bug bash: Parameter location is locked to param block in function
Issue -
State: open - Opened by mattchenderson about 2 years ago
#40 - Bug bash: CurrentUtcDateTime not getting updated with DurableTimers
Issue -
State: open - Opened by michaelpeng36 about 2 years ago
#39 - Bug bash: Update profile.ps1 to rename MSI_SECRET
Issue -
State: open - Opened by mattchenderson about 2 years ago
#38 - Bug Bash: Unable to find `profile.ps1` in the function app root folder
Issue -
State: open - Opened by michaelpeng36 about 2 years ago
#37 - Update AzureFunctions.PowerShell.SDK module
Pull Request -
State: closed - Opened by Francisco-Gamino about 2 years ago
#36 - Update module PowerShell SDK to 7.2.11
Issue -
State: closed - Opened by Francisco-Gamino about 2 years ago
#35 - Automate publishing AzureFunctions.PowerShell.SDK to the PowerShellGallery via CI
Issue -
State: open - Opened by Francisco-Gamino about 2 years ago
#34 - Publish AzureFunctions.PowerShell.SDK to the PowerShellGallery.com
Issue -
State: open - Opened by Francisco-Gamino about 2 years ago
#33 - Ensure we have a good dev experience when developing functions locally (similar to PyStein)
Issue -
State: open - Opened by Francisco-Gamino about 2 years ago
#32 - Ensure that PowerShell SDK version between the worker and this library are consistent
Issue -
State: open - Opened by andystaples about 2 years ago
#31 - try/catch for ReflectionTypeLoadException might be unnecessary
Issue -
State: open - Opened by andystaples about 2 years ago
#30 - What happens when attribute names are shadowed?
Issue -
State: open - Opened by andystaples about 2 years ago
#29 - Bug bash: Defining an HttpTrigger only with Authorization fails to execute
Issue -
State: open - Opened by Francisco-Gamino over 2 years ago
#28 - Bug Bash: No intellisense of SDK annotations
Issue -
State: open - Opened by davidmrdavid over 2 years ago
#27 - Bug Bash: DurableClient's `Name` parameter does not seem to control any user-code variables
Issue -
State: open - Opened by davidmrdavid over 2 years ago
#26 - Bug bash: Functions Host file watcher does not work with the new programming model
Issue -
State: open - Opened by Francisco-Gamino over 2 years ago
#25 - Bug bash: PowerShell worker requires the AzureFunctions.PowerShell.SDK module to be available in the global PSModulePath
Issue -
State: open - Opened by Francisco-Gamino over 2 years ago
#24 - AdditionalInformation compability with Output Bindings
Pull Request -
State: closed - Opened by andystaples over 2 years ago
#23 - AdditionalInformation is an Input binding, it should be supported as both input and output
Issue -
State: open - Opened by andystaples over 2 years ago
#22 - Change from positional to named arguments
Pull Request -
State: closed - Opened by andystaples over 2 years ago
#21 - Fixes for various module issues
Pull Request -
State: closed - Opened by andystaples over 2 years ago
#20 - Should we error out if we parse a directory with no bindings?
Issue -
State: closed - Opened by Francisco-Gamino over 2 years ago
- 1 comment
#19 - How should you detect know key value pairs? Validation for AdditionalInformation parameters
Issue -
State: open - Opened by Francisco-Gamino over 2 years ago
#18 - Add support for Piping
Issue -
State: closed - Opened by Francisco-Gamino over 2 years ago
- 1 comment
#17 - Normalize path to add support for relative paths
Issue -
State: closed - Opened by Francisco-Gamino over 2 years ago
- 1 comment
#16 - Check for host.json to ensure that this is the function app root before parsing
Issue -
State: closed - Opened by Francisco-Gamino over 2 years ago
#15 - Generic Binding improvement
Pull Request -
State: closed - Opened by andystaples over 2 years ago
#14 - Set up CI with Azure Pipelines
Pull Request -
State: closed - Opened by Francisco-Gamino over 2 years ago
- 1 comment
#13 - Move tests to root folder
Pull Request -
State: closed - Opened by andystaples over 2 years ago
#12 - Build script fully qualified name issue
Issue -
State: open - Opened by andystaples over 2 years ago
#11 - Code does not work with NamedArguments in cmdlet or function attributes
Issue -
State: closed - Opened by andystaples over 2 years ago
#10 - cmdlet returns metadata even if functions with duplicate names exist
Issue -
State: closed - Opened by andystaples over 2 years ago
- 1 comment
#9 - Build script flags untested
Issue -
State: open - Opened by andystaples over 2 years ago
#8 - Defaults hard-coded in the binding classes implemented from IBinding
Issue -
State: closed - Opened by andystaples over 2 years ago
- 1 comment
#7 - Various binding types not supported
Issue -
State: open - Opened by andystaples over 2 years ago
- 1 comment
#6 - Build script deploys the module to the local Core Tools install, but not to the PSModulePath
Issue -
State: open - Opened by andystaples over 2 years ago
#5 - Intellisense/VS code usability features not present
Issue -
State: open - Opened by andystaples over 2 years ago
#4 - No CI/CD pipeline
Issue -
State: closed - Opened by andystaples over 2 years ago
#3 - Generic binding/Addl binding parameters not supported
Issue -
State: closed - Opened by andystaples over 2 years ago
#2 - No tests exist for this project
Issue -
State: closed - Opened by andystaples over 2 years ago
- 2 comments
#1 - Initial commit
Pull Request -
State: closed - Opened by andystaples over 2 years ago
- 2 comments